Title: This week in WordPress Accessibility, February 12, 2018
Author: Sami Keijonen
Published: February 12, 2018

---

 [  ](https://profiles.wordpress.org/samikeijonen/) [Sami Keijonen](https://profiles.wordpress.org/samikeijonen/)
6:25 pm _on_ February 12, 2018      

# This week in WordPress Accessibility, February 12, 2018

[Transcript of a meeting in Slack](https://wordpress.slack.com/archives/C02RP4X03/p1518454818000194).

## Handbook

[@rianrietveld](https://profiles.wordpress.org/rianrietveld/) and [@samikeijonen](https://profiles.wordpress.org/samikeijonen/)
worked on AccessibilityAccessibility Accessibility (commonly shortened to a11y) 
refers to the design of products, devices, services, or environments for people 
with disabilities. The concept of accessible design ensures both “direct access”(
i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive
technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/
Accessibility) Handbook in [WordCamp Jyväskylä](https://2018.jyvaskyla.wordcamp.org/).
They decided to take over writing the articles so that handbook is done quicker 
and more uniform. Naturally lot’s of help is needed:

 * gathering resources
 * gathering topics
 * review texts

## aria-label wording in navigation landmark

We should avoid word _navigation_ in aria-label when using navigation landmark. 
For example `<nav aria-label="Primary navigation">` will be announced as **Primary
navigation navigation** because screen readers add the word navigation by themselves.

One option is remove word navigation: `<nav aria-label="Primary">`. Or use other
wording like `<nav aria-label="Primary Menu">`.

## GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. 󠀁[https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)󠁿 status

[@afercia](https://profiles.wordpress.org/afercia/) had couple issues he would consider
the minimum required for version 1:

 * Implement navigation mode / edit mode for the blocks.
 * A method to constrain tabbing within components that need to be treated as sort
   of “modals”.

## Accessibility support forumSupport Forum WordPress Support Forums is a place to go for help and conversations around using WordPress. Also the place to go to report issues that are caused by errors with the WordPress code and implementations. status

We should check more frequently [accessibility support forum](https://wordpress.org/support/forum/accessibility/).
At the moment there is no assigned people who do that.

## Navigation landmark inside headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. landmark

Given that assistive technologies don’t behave the same way with nested landmarks,
we should try to avoid nested landmarks. In reality it’s really common to have `
<nav>` inside `<header>`. Mostly because of the design.

More investigation and testing should be done to get more details and issues about
nested landmarks.

### Share this:

 * [  Threads ](https://make.wordpress.org/accessibility/2018/02/12/this-week-in-wordpress-accessibility-february-12-2018/?share=threads)
 * [  Mastodon ](https://make.wordpress.org/accessibility/2018/02/12/this-week-in-wordpress-accessibility-february-12-2018/?share=mastodon)
 * [  Bluesky ](https://make.wordpress.org/accessibility/2018/02/12/this-week-in-wordpress-accessibility-february-12-2018/?share=bluesky)
 * [  LinkedIn ](https://make.wordpress.org/accessibility/2018/02/12/this-week-in-wordpress-accessibility-february-12-2018/?share=linkedin)
 * [  X ](https://make.wordpress.org/accessibility/2018/02/12/this-week-in-wordpress-accessibility-february-12-2018/?share=x)
 * [  Facebook ](https://make.wordpress.org/accessibility/2018/02/12/this-week-in-wordpress-accessibility-february-12-2018/?share=facebook)

 1. Pingback: [Accessibility team update, February 12, 2018 – Team Updates — WordPress](https://make.wordpress.org/updates/2018/02/19/accessibility-team-update-february-12-2018/)

Comments are closed.

# Post navigation

[← This week in WordPress Accessibility, December 18, 2017](https://make.wordpress.org/accessibility/2017/12/18/this-week-in-wordpress-accessibility-december-18-2017/)

[This week in WordPress Accessibility, February 26, 2018 →](https://make.wordpress.org/accessibility/2018/02/26/this-week-in-wordpress-accessibility-february-26-2018/)