DouglasCountyCO / Accessibility-PowerBI-Reports-Public

This repository represents accessibility results from testing power bi reports. The initial report addressed in this fashion is the Foreclosure Search "AppOwnsData" embedded , but the expectation is that
2 stars 0 forks source link

FS Details Rpt: Redemption Page: Keyboard / Tab Order #18

Open KTottenDC opened 3 months ago

KTottenDC commented 3 months ago

Current Tab Order

  1. Public Trustee Resources -- Box O'Links image -- Enter and down arrow read everything but the Additional Resources - this may need to be addressed. The arrow also provided "scroll down" access in the box of links. Down arrow continued to proceed to the map, but a tab put us into DOT Reception and Recording Date.

  2. DOT Reception and Recording Date image -- This should be picking only the top item. Should it really have multiple recording dates?

  3. NED Reception and Recording Date image

  4. Post-Sale Information image -- This should be sorted most recent to oldest. Scroll bars will be hard to navigate, so also consider making this another page.

5.Links image -- Note the links in the links page. They should read as a link. Not sure why this needs so many columns, but again I would sort so that the most recent show up in the first visible column position.

  1. Redemption Button Group -- Definitely the wrong tab order. image -- TODO: Either start or stop with this group of buttons. Stopping would make sense considering there is no "back" button. So, a keyboard navigator will want to end there after tabbing around to allow them to get to other pages in the report.

7.Redemption -- (Grid Info) image -- TODO: Sort the grid so that the first columns are the most recent data as a sight impaired person will not automatically know that there is a scroll bar to get the most recent information. -- Down arrow works fine.

8.Map image -- TODO: Big tool tips are great for sighted people, but they are ill-advised for accessibility. Consider removing unless the screen reader can get at them. -- TODO: Name the map (separate test), label and allow a keyboard navigator to recognize and read the control buttons. Label the data points as they should not be just delineated by color (separate test). Ensure the legend can be tabbed or read by a screen reader (separate test).

Again - tab order is definitely incorrect since there is no back button and the navigation "button group" is landed on in the middle of tabbing.