Fennec/Features/a11y
Status
| Support users with disabilities | |
| Stage | Development |
| Status | In progress |
| Release target | ` |
| Health | OK |
| Status note | Implementation in progress. |
{{#set:Feature name=Support users with disabilities
|Feature stage=Development |Feature status=In progress |Feature version=` |Feature health=OK |Feature status note=Implementation in progress. }}
Team
| Product manager | Thomas Arend |
| Directly Responsible Individual | Thomas Arend |
| Lead engineer | ` |
| Security lead | ` |
| Privacy lead | ` |
| Localization lead | ` |
| Accessibility lead | David Bolter, Fernando Herrera |
| QA lead | ioana.chiorean [ioanachiorean irc] [e-mail] |
| UX lead | Brian Dils |
| Product marketing lead | ` |
| Operations lead | ` |
| Additional members | ` |
{{#set:Feature product manager=Thomas Arend
|Feature feature manager=Thomas Arend |Feature lead engineer=` |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=David Bolter, Fernando Herrera |Feature qa lead=ioana.chiorean [ioanachiorean irc] [e-mail] |Feature ux lead=Brian Dils |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}
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
` {{#set:Feature open issues and 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
|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 |Feature users and use cases=` |Feature dependencies=` |Feature requirements=* See PRD at http://bit.ly/fenneca11y |Feature non-goals=` |Feature functional spec=` |Feature ux design=` |Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=` |Feature landing criteria=` }}
Feature details
| Priority | P3 |
| Rank | 999 |
| Theme / Goal | ` |
| Roadmap | Firefox Mobile |
| Secondary roadmap | ` |
| Feature list | Mobile |
| Project | ` |
| Engineering team | Mobile front-end |
{{#set:Feature priority=P3
|Feature rank=999 |Feature theme=` |Feature roadmap=Firefox Mobile |Feature secondary roadmap=` |Feature list=Mobile |Feature project=` |Feature engineering team=Mobile front-end }}
Team status notes
| status | notes | |
| Products | ` | ` |
| Engineering | ` | ` |
| Security | ` | ` |
| Privacy | ` | ` |
| Localization | ` | ` |
| Accessibility | ` | ` |
| Quality assurance | ` | ` |
| User experience | ` | ` |
| Product marketing | ` | ` |
| Operations | ` | ` |
{{#set:Feature products status=`
|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=` |Feature security health=` |Feature security notes=` |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=` |Feature qa notes=` |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}