[2.2.x./2.3.x, Accessibility] Apply accessibility guidelines in the features that have been developed in the latest releases by the MAAS team and are not accessible

Bug #1722863 reported by Maria Vrachni
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Undecided
Maria Vrachni

Bug Description

[2.2.x./2.3.x, Accessibility] Apply accessibility guidelines in the features that have been developed in the latest releases by the MAAS team and are not accessible

A number of features have been implemented in the last two releases that do not comply with the accessibility guidelines (Aria labels, tabbing through the UI etc)

Bug description:

* Current result:

Given I am the MAAS web application following the 2.1 release
When I am trying to access the new features with my keyboard or a screen reader
Then I probably can't

* Expected/ correct result:

Given I am the MAAS web application following the 2.1 release
When I am trying to access the new features with my keyboard or a screen reader
Then I should be able to

[OS X Sierra]

Chrome, Version 61.0.3163.79 (Official Build) (64-bit)

Screen size: 15.4-inch (2880 x 1800)

Changed in maas:
assignee: nobody → Maria Vrachni (m-vrachnis)
Changed in maas:
milestone: none → 2.3.0beta3
Changed in maas:
milestone: 2.3.0beta3 → 2.3.0beta4
Changed in maas:
milestone: 2.3.0beta4 → next
Changed in maas:
status: New → Invalid
Changed in maas:
milestone: next → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.