<scribe> scribe: kathy
<Wilco> https://docs.google.com/spreadsheets/d/1OSkPFocXk4K3zYLnwS78WLsWO4PvE5yRcsauyefuIUI/edit#gid=0
wilco: one more thing open.
description track went into call for review today
... once merged, will migrate and push in one PR
<Wilco> https://github.com/act-rules/act-rules.github.io/pulls
wilco: 2 PRs open by Trevor,
already have 1 approval.
... change "recommend" to "required"
daniel: I will review also
wilco: next #1694 add funding to
acknowledgement to track tool written under wai tools.
currently all but one are. need to distinguish those
... will add a sentence about wai tools funding
... have 1 approval
Karen: I will review
aron: I will review
trevor: can we see how it will render?
wilco: removed acknowledgements
from heading to footer
... scroll to bottom
... next, update def of included in accessibility tree, need
reviews
... next, update line height
trevor: need more time
wilco: next PR #64 will be merged
wilco: survey 1 letter spacing.
type PR already merged.
... I will update Accessibility Support but not blocking
because of it
... isn't clear how Accessibility Support relates to SC so
needs clarification
... rule targets tools like stylish bookmark which isn't
typical AT
... no objections to move rule forward
wilco: I've been working on site
update with Shawn's feedback
... added intro text to both rules, updated summary, need to
update WCAG 2 Test Rules heading
... Rules pages updated with icons, acknowledgement moved to
footer
... table of contents in summary box on rule example
<shawn> https://github.com/w3c/wcag-act-rules/issues/57#issuecomment-902240280
shawn: usability testing in 2017
for redesign, in prototype some pages had toc some didn't
... users wanted summary and toc at beginning of every page.
helps orient to page and jump to sections. mostly for
orientation
... default redesign would include toc on every page
... toc also provided anchor link to send url
... EO also noted toc would be useful
... want to understand if user exp would improve without
toc
... as user who is updating my eval tool and need to
incorporate a test rule scenario. how often will a user want to
jump to a specific section vs read from top to bottom?
aron: I've read every rule. big
learning curve when joining community. I glanced over acc req
mapping to see if atomic or composite.
... reading top to bottom
... but now jump to sections
kathy: on first read, I would read top to bottom but revisiting, would jump to test cases mostly
trevor: similar, jump between test cases and expectations
daniel: can see use case of going back and forth
shawn: support common use of read through then jump to test cases and expectations. propose a small toc to enable back and forth
kathy: if toc is at top of the page, going from test cases to expectations would scroll past the content I want, so I wouldn't need to go to top of page toc
shawn: do you want to go to test cases in general or jump to fail?
wilco: I usually look for a specific one
shawn: I have some ideas, will work with wilco and hidde to improve user experience for everyone
aron: like background for code examples in cg pages
wilco: talked to hidde about different colors, might be able to do
shawn: I would support that
hidde: other color scheme might be used on other pages
wilco: can these pages move forward with plan to add toc?
shawn: will use this as template
for other pages, let's see if we can get it done in the next
week
... if want to publish, add toc now and then consider changing
it later
<hdv> current: https://www.w3.org/WAI/standards-guidelines/act/rules/html-page-non-empty-title-2779a5/
wilco: adding toc is a lot of work, need to write script
shawn: page content is generated from headings in wai site
hidde: will send link to wilco
shawn: toc on understanding and techniques pages?
hidde: yes and no, some are long
shawn: shorter toc based on user
exp that were shared
... would be nice to have example with toc
wilco: will send page with toc
wilco: survey 2, agreement to
trevor's comment
... passed ex 6 comment ignore
... aron's comment on open issues. 1686 do not think is a
blocker
trevor: what if zoom in to make single line of text to more than one line?
wilco: in theory, items in a menu
will not be multi-line ever
... edge case that we don't need to worry about
trevor: would this change applicability or assumption
aron: edge case of menu item with
line height style set to important
... very unlikely
wilco: #1687 no content in a div
with letter spacing still fails.
... wrap letter spacing with letter spacing would also be a
problem
... #1688 also edge cases
... propose move forward with PRs open
trevor: working with jean yves on one
karen: have seen some of those edge cases in wild.
<shawn> Hi Wilco. I have another idea that I think might work much better to improve usability. So, don't spend time on a TOC yet. I hope to send email with my idea within an hour
<Wilco> Thanks Shawn. I'll wait for that.