Fennec/Features/a11y

Status

Team

Open issues/risks

• Use PRD at http://bit.ly/fenneca11y to identify, document (Bugzilla) and prioritize specific A11y features and requirements
• Prioritize those features in our Mobile Priorities master list

Stage 1: Definition

1. Feature overview

Browsers on mobile touch-enabled devices, like smartphones and tablets, need full support for people with disabilities. Small screens and virtual keyboards can sometimes be difficult to use, even for people with perfect vision. Firefox for mobile does not currently have any accessibility features. We should integrate with Android OS services and also build new accessibility features to cater to all users, also ones that are not missing any of their faculties or abilities ("curb-cut-effect"). This document describes use cases and requirements for making Firefox fully accessible on Android devices.

See full PRD at http://bit.ly/fenneca11y

2. Users & use cases

`

3. Dependencies

`

4. Requirements

• See PRD at http://bit.ly/fenneca11y

Non-goals

`

Stage 2: Design

5. Functional specification

`

6. User experience design

`

Stage 3: Planning

7. Implementation plan

`

8. Reviews

Security review

`

Privacy review

`

Localization review

`

Accessibility

`

Quality Assurance review

`

Operations review

`

Stage 4: Development

9. Implementation

`

Stage 5: Release

10. Landing criteria

`

Feature details

Team status notes