<CarlosD__> scribe+ markrogers

take up next

zakim take up next

ACT stand-up

Carlos: busy on other stuff

Mark: been doing screen reader testing www.powermapper.com/tests

most AT has got better, some stuff worse (img alt inside button not read as acc name, iframe role=presentation still a problem)

wilco: doing pull requests, working through updates

helen: viral post on Dan's work on voice navigation

kathy: PR for rule format changes to address comments, wrapped annual review

jean-yves: CSUN presentation on ACT Rules accepted

ACT TF update

wilco: updates to existing rules with kathy

Reminder: book flight/hotel for face to face meeting

<CarlosD__> https://github.com/act-rules/act-rules.github.io/wiki/2025-F2F-meeting-Edinburgh

mark: we'll send out a few restaraunt alternatives

Applicability in color contrast rules

<CarlosD__> https://github.com/act-rules/act-rules.github.io/issues/2215

carlos: links without href and aria-disabled are being flagged by the rule

jean-yves: removing href means it's no longer a widget and probably fails 1.3.1
... should there be a test case for this, and is this a true positive?

carlos: don't want to encourage people using aria-disabled on a without href

jean-yves: should be more than just in the banckground

dan: this an example where you do need to use aria

kathy: in the assumptions do we want to keep the aria-disabled text if we don't want to encourage aria misuse
... the disabled definition should be in the assumption

jean-yves: but we normally try to avoid that

helen: exposes the aria programatic attributes, but you still need other attrs like tabindex
... anything that can be native, should be natvie

kathy: aria-disabled is used a lot in the inapplicable examples

jean-yves: have do examples with explicit role, even if this can be with html

carlos: aria-disabled here has no function when there is no href

jean-yves: maybe we should add styling and event handlers to some of the examples

dan: would this address your concerns

kathy: I think so, but I need to re-read Jean-Yves issue a little further

jean-yves: looks like Inapplicable Example 9 breaks the rules assumption
... but this is a different problem

kathy: what would clear it up is changing the assumption in the definition

carlos: I think we need both

jean-yves: or we decide Inapplicable Example 11 is bad, but I feel uncomfortable with that

carlos: definition of disabled element but Inapplicable Example 11 is inoperable, not disabled
... perhaps we should write the definition to take account of inoperable (because aria-disabled doesn't make it inoperable, lack of href does)

jean-yves: then we don't need the assumption and remove Inapplicable Example 9

carlos: i agree

kathy: that makes sense

jean-yves: that may not resolve the issue I raised

helen: if you remove href it still works with a mouse
... so it's a 4.1.2 issue

carlos: modify the assumption, then add a paragraph to background about removing href not being acceptable
... we'll discuss in the PR

Viewport size for text resize rule

<CarlosD__> https://github.com/act-rules/act-rules.github.io/issues/2216

carlos: we need to consider the width requirement for horzontally written languages, and height for vertically written languages

giacomo: a commong example is a manual that is not scrollable when zoomed

jean-yves: example of a cookie banner that was not scrollable when zoomed, so can;t access to accept/reject buttons

carlos: we have examples of vertical and horizontal overflow

wilco: I thought we'd addressed this in the rule but can't see this anywhere

carlos: looking at old version of rule. "1.4.10 doesn't require a vertical scrolling page to meet a height. This is a common misconception."

wilco: this is kind of an arbitrary decision but its the closest to normative value we've got

carlos: it could be even smaller

wilco: it's a weird resolution, but it's in WCAG 2
... I think that's the anser, it's ever changing, but we need to pick something

carlos: so it's in WCAG 2.2 1.4.10 ?
... but we're checking a different SC in this rule

dan: can we put those words in the rule: "we had to choose something"

wilco: it is assumed 1280x1024 is applicable because it's mentioned in 1.4.10

carlos: I'll reply

This is scribe.perl Revision VERSION of 2020-12-31
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Default Present: CarlosD__, Jean-Yves, Helen, Dan_Tripp, markrogers, Kathy, Jeremy, giacomo-petri, Wilco
Present: CarlosD__, Jean-Yves, Helen, Dan_Tripp, markrogers, Kathy, Jeremy, giacomo-petri, Wilco
No ScribeNick specified.  Guessing ScribeNick: markrogers
Inferring Scribes: markrogers

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth


WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)