Closed Bug 886111 Opened 12 years ago Closed 12 years ago

Add Accessibility to "In depth" list on main page

Categories

(developer.mozilla.org Graveyard :: General, defect)

Product:
developer.mozilla.org Graveyard
Component:
General
Platform:
All
Other
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jswisher, Unassigned)

Details

(Whiteboard: [specification][type:change])

What feature should be changed? Please provide the URL of the feature if possible. ================================================================================== On the MDN home page, add Accessibility in the "In depth" section, with a link to the accessibility landing page: https://developer.mozilla.org/en-US/docs/Accessibility What problems would this solve? =============================== Accessibility is an important topic for web developers, which currently has no visibility on the home page. Who would use this? =================== Web developers who want to know more about accessibility, and those who may not be aware that it is a topic they should be interested in . What would users see? ===================== What would users do? What would happen as a result? =================================================== Is there anything else we should know? ======================================
Could we add this under "Web Basics" instead; I think accessibility is more of a topic. The items under "In Depth" are tutorial types and non-web-doc specific.
This came up during the doc sprint last weekend, and the consensus in the room was that "Web Basics" seemed to be technologies, whereas "In Depth" was things accessibility, apps, and dev tools cut across technologies and are predicated on them. You can do it either way -- the main thing is to get it on the list. But consider this as some user feedback on the information architecture.
Janet and I had a conversation about this during the last sprint. In many ways, accessibility is a cross over subject that requires to have basic knowledge before starting being able to really understand the needs and the technics required to make a web content accessible. In many ways, it's about how to use the technical parts of the web rather than learning some new technologies. In that sens I think it's closer than tutorials and guides rather than a web topic in itself. If we want to add something under "Web Basics" to support accessibility, I would rather add a direct access to the ARIA part https://developer.mozilla.org/en-US/docs/Accessibility/ARIA which is less general and more what I imagine as a "basic" stuff.
Commits pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/6dd8df00bb5a9d86d3029e96062240013258b906 fix bug 886111 - Add a11y to menu and homepage https://github.com/mozilla/kuma/commit/34e013557a9b54a8f0ca088065f60c628afe5b93 Merge pull request #1196 from darkwing/a11y-886111 fix bug 886111 - Add a11y to menu and homepage
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.