Add C# Extensions for Accessibility APIs

[TheCodeTraveler]

Let's add C# Extension Methods for the following Accessibility APIs:

• Element
  • AutomationId
• SemanticProperties
  • SemanticProperties.DescriptionProperty
  • SemanticProperties.HeadingLevelProperty
  • SemanticProperties.HintProperty
• AutomationProperties
  • AutomationProperties.ExcludedWithChildrenProperty
  • AutomationProperties.HelpTextProperty
  • AutomationProperties.IsInAccessibleTreeProperty
  • AutomationProperties.LabeledByProperty
  • AutomationProperties.NameProperty

[pictos]

I approve this feature ✅

[jfversluis]

Me too! This explains why I couldn't find this just now :D

[bijington]

I also approve

[mrlacey]

Apart from the following, it seems all of these have been implemented.

• AutomationProperties.HelpTextProperty
• AutomationProperties.LabeledByProperty
• AutomationProperties.NameProperty

Is there a reason not to include these?

[bijington]

Perhaps we should mark this reason explicitly somewhere

[mrlacey]

I thought this was probably the case but there's no such superseded notice on the docs pages for those properties. That's where I'd expect to see it recorded.

Perhaps we should mark this reason explicitly somewhere

I think that as it's now documented here it should be sufficient. If you wanted to be really thorough, we could add them with an Obsolete attribute to point people towards using the SematincProperties instead.

[bijington]

Paging @jfversluis do you know whether these AutomationProperties really are deprecated or whether the docs should mention them being superseded by SemanticProperties.

On the idea of adding them and marking as Obsolete I think I like the idea. It certainly makes it more discoverable and means we don't have to say RTFM. @brminnick do you have any thoughts?

[TheCodeTraveler]

If you wanted to be really thorough, we could add them with an Obsolete attribute to point people towards using the SematincProperties instead

On the surface, it does seem silly to add a new API with the [Obsolete] attribute, but I actually think this is a good idea and makes a lot of sense!

[jfversluis]

@rachelkang @PureWeen are the accessibility wizards!