⚓ T107213 Blueprint should make use of HTML5 <header> and <main> element with correct ARIA roles

	Subject	Repo	Branch	Lines +/-
	Use HTML5 sectioning elements and ARIA roles	mediawiki/skins/Blueprint	master	+355 -18

Status	Assigned	Task
Resolved	• Spage	T307 Announcing the Developer Hub prototype release
Resolved	• Spage	T299 Release the Developer Hub prototype
Resolved	• Spage	T306 Featuring the first three APIs in the Developer Hub
Resolved	ori	T334 Document RCStream in the Developer Hub
Declined	None	T302 API sandboxes for the Developer Hub
Resolved	None	T300 Select the three APIs featured at the Developer Hub prototype
Declined	None	T88755 Improve MediaWiki API example behavior
Resolved	Anomie	T89229 API Help should generate [try in ApiSandbox] link to Special:ApiSandbox#action=params from getExamples()
Declined	None	T89318 Replace on-wiki API documentation with Special:ApiHelp transclusion
Open	None	T89768 Language support in Special:ApiHelp and its transclusion.
Open	None	T90528 Generated API Help doesn't indicate the MediaWiki versions that support a module and parameters.
Resolved	• Spage	T89680 Template:ApiEx on mw.org should have a link to "[view in ApiSandbox]".
Declined	None	T335 Document the Content API in the Developer Hub
Resolved	jeropbrenda	T359 Document the Wikidata API in the Developer Hub
Open	None	T89863 [Task] Merge on-wiki Wikibase/API documentation into Wikibase apihelp strings.
Declined	Qgil	T303 Setup the Developer Hub prototype
Resolved	• Spage	T98164 prototype Data and developer hub with Blueprint skin
Resolved	Qgil	T101099 Developer Relations Roadmap
Resolved	Qgil	T113030 Developer Relations quarterly review Jul-Sep 2015
Resolved	Qgil	T101100 Engineering Community quarterly goals for July-September 2015
Resolved	• Spage	T101441 Goal: Integrate the new Web APIs hub with mediawiki.org
Resolved	• Spage	T305 Developer Hub homepage
Resolved	• Spage	T301 Define the look&feel of the Developer Hub
Declined	None	T93062 Define the navigation elements of the Web APIs hub
Declined	None	T317 "Terms of Use" must be prominently featured in the Developer Hub
Resolved	• Spage	T92941 Define personas for dev.wikimedia.org
Resolved	• Spage	T92945 Reflect in dev.wikimedia.org what Wikimedia offers to developers
Declined	None	T93610 Put WikimediaUI Style Guide on mediawiki.org
Declined	None	T93613 Deploy Blueprint on mediawiki.org as optional and experimental skin
Declined	None	T112487 Blueprint HTML output lacks headings (document) structure
Resolved	None	T110983 Blueprint sidebar reuses #firstHeading id
Declined	None	T103986 issues with Data and Developer Hub prototype (tracking)
Declined	None	T110835 `blueprint-left-nav` message doesn't seem to be localizable
Resolved	Volker_E	T111117 [EPIC] Enhance accessibility of OOUI & MediaWiki UI library / LSG / MediaWiki General to screen readers and color-deficient users
Resolved	None	T88023 Create landmarks for screen reader
Resolved	• Prtksxna	T104288 Blueprint skin has no footer or replacement (so no copyright)
Resolved	Volker_E	T107213 Blueprint should make use of HTML5 <header> and <main> element with correct ARIA roles

Volker_E created this task.Jul 28 2015, 9:03 PM

Volker_E claimed this task.

Volker_E raised the priority of this task from to Medium.

Volker_E updated the task description. (Show Details)

Volker_E added subscribers: • Prtksxna, • Spage.

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJul 28 2015, 9:03 PM

Volker_E renamed this task from Blueprint should use a `<header>` element with a correct ARIA role to Blueprint should make use of HTML5 `<header>` and `<main>` element with correct ARIA roles.Jul 28 2015, 9:12 PM

Volker_E updated the task description. (Show Details)

Volker_E set Security to None.

Volker_E added a project: Accessibility.

Volker_E moved this task from Backlog to Needs Review / Feedback on the Blueprint board.Jul 28 2015, 10:14 PM

Volker_E mentioned this in T88023: Create landmarks for screen reader.Jul 28 2015, 11:35 PM

Volker_E renamed this task from Blueprint should make use of HTML5 `<header>` and `<main>` element with correct ARIA roles to Blueprint should make use of HTML5 <header> and <main> element with correct ARIA roles.Aug 2 2015, 10:37 PM

Change 227582 had a related patch set uploaded (by Prtksxna):
Make use of HTML5 sectioning elements

https://gerrit.wikimedia.org/r/227582

gerritbot added a project: Patch-For-Review.Aug 3 2015, 10:56 AM

As MediaWiki 1.26 is currently integrating jQuery 1.11.3 it's not yet providing support for `<main>´ element in IE<9.
Therefore we need to include html5shiv-printshiv.js as well. Why html5shiv-printshiv and not just html5shiv? Blueprint is us for the Living Style Guide, there is a probabiliy for people printing pages.

Change 227582 abandoned by VolkerE:
Make use of HTML5 sectioning elements

Reason:
abandoning this, starting with new patch

https://gerrit.wikimedia.org/r/227582

Change 227582 restored by VolkerE:
Make use of HTML5 sectioning elements

Reason:
reverting wrong decision beforehand

https://gerrit.wikimedia.org/r/227582

Volker_E added a subscriber: • pizzzacat.Aug 30 2015, 4:57 PM

@Prtksxna (Commenting here again, aside from T88023) Latest patch set #4 includes role="navigation" and footer[role="contentinfo"].
I've also altered markup order, so that <header> comes before <nav> for better screen-reader/keyboard user experience and added a skip-to-nav link.

A question still open is translation of skip link. Is [[ https://www.mediawiki.org/wiki/Manual:Messages_API#Language | wfMessage() ]] the right approach?

• violetto added a parent task: T111117: [EPIC] Enhance accessibility of OOUI & MediaWiki UI library / LSG / MediaWiki General to screen readers and color-deficient users.Sep 1 2015, 10:10 PM

In T107213#1587925, @Volker_E wrote:

A question still open is translation of skip link. Is [[ https://www.mediawiki.org/wiki/Manual:Messages_API#Language | wfMessage() ]] the right approach?

Looks like the right way to go about this, yes!

@Prtksxna I'd prefer to go for another task caring about i18n and just merge that with changes included so far.

Opened T112308 on skip-links.

Volker_E added a parent task: T88023: Create landmarks for screen reader.Sep 12 2015, 3:15 AM

Volker_E added a parent task: T110983: Blueprint sidebar reuses #firstHeading id.Sep 13 2015, 11:45 PM

Volker_E mentioned this in T112487: Blueprint HTML output lacks headings (document) structure.Sep 14 2015, 12:30 AM

Volker_E added a parent task: T112487: Blueprint HTML output lacks headings (document) structure.

Volker_E added a parent task: T93613: Deploy Blueprint on mediawiki.org as optional and experimental skin.Sep 24 2015, 1:57 AM

As a comment by @Pastakhov went about necessity of including ARIA landmark role attributes, instead of relying to native semantic roles:
As long as not all browsers (ex: Fx<21, Ch<26) map the ARIA landmark roles to the elements, it's recommended to include the role attributes. See f.e. on `role="main" over at http://html5doctor.com/the-main-element/#comment-35495