Windowscommunitytoolkit: Apply our accessibility min-bar to controls

Created on 30 Sep 2016  路  12Comments  路  Source: windows-toolkit/WindowsCommunityToolkit

  • [x] AdaptiveGridView
  • [x] RangeSelector
  • [x] HamburgerMenu
  • [x] BladeView
  • [x] DropShadowPanel
  • [x] HeaderdTextBlock
  • [x] ImageEx
  • [x] PullToRereshListView
  • [x] RotatorTile
  • [x] SlidableListItem
  • [x] MarkdownTextblock
  • [x] DropShadowPanel
  • [x] TextBoxMask
  • [x] TextBoxRegex
  • [x] Expander
  • [x] TileControl
  • [x] WrapPanel

  • [x] GridSplitter

  • [x] MasterDetailsView
  • [x] RadialGauge

More info on the features to check:
https://github.com/Microsoft/UWPCommunityToolkit/blob/dev/contributing.md#quality-insurance-for-pull-requests-for-xaml-controls

controls help wanted improvements

Most helpful comment

Working on a blog post to explain more how to do this

All 12 comments

Working on a blog post to explain more how to do this

It is perfect and AutomationProperies implementation must be a requirement for any project out there. I used to work with blind-born programmer and he was mentioning about this everytime. Why it is important, why we should have it etc. It also helps to keep up with our main reason which is helping developers.

I'm glad :)

Here is the blog post: https://www.eternalcoding.com/?p=2792

I'm in ! I start with the HeaderdTextBlock control.

Thanks!

just check this PR first as we are introducing some update to the control:

489

For the HeaderdTextBlock control, Name and AutomationProperties.Name are filled. I think it's already good, isn't it ?

Correct :) I flagged it as done

I continue with the PullToRefreshListView control.

I continue with the SlidableListItem control.

It's done with the SlidableListItem control, I continue with the GridSplitter control.

Almost done. Need to finish radial gauge and I'll send a PR

Was this page helpful?
0 / 5 - 0 ratings