The same could apply to descriptions (e.g. a description could include a link
to more info about how to fill in the field), but that's never been a factor
before. Also, even if you believe this is more likely with errormessage for
some reason, I'm guessing you still want AT to report the
We want to separate out errors from help information. aria-errormessage only
takes an IDREF.
> On Feb 24, 2016, at 5:14 PM, James Teh wrote:
>
> I thought aria-describedby could refer to multiple nodes. As such, I don't
> follow why authors were "stuck" when they wanted
Error messages may have additional content in there that needs greater semantic
structure. For example, what if the error message had a link to a online help
area about the topic. Converting it to a string would not work.
Rich
> On Feb 23, 2016, at 5:20 PM, Joanmarie Diggs
Part of the rationale for introducing aria-errormessage was that authors
were already using aria-describedby for the error message, but were
stuck when they wanted to provide a description separate from the error
message. Thus, a reason for introducing aria-errormessage was to
distinguish it
On 2016-02-23 10:48 PM, Rich Schwerdtfeger wrote:
We will update the ARIA mapping spec
Can you be more specific? One thing we will do is change the mapping
for role region to:
"IAccessible2: IA2_ROLE_LANDMARK and object attribute xml-roles:region".
For comparison, the current ATK/AT-SPI
On 2016-02-23 6:30 PM, Joanmarie Diggs wrote:
... sucks dirty socks IMHO
Eeww. Thank you so much for that image :-(
--
joseph.
'Die Wahrheit ist Irgendwo da Draußen. Wieder.'
- C. Carter -
___
Accessibility-ia2 mailing list