Meeting minutes
Status of Site Updates
MK: Publication last week, next October 31st, could delay if needed
MK: Would like a Nov and Dec updates
MK: Three things to get done
MK: Menu button examples
AC: I will look at it this week
JG: Regression test changes
MK: Yes, I did put in the issue in the regression test needs to be changed
MK: I will get the keyboard changes
MK: The feed example is a stretch
MK: Maybe the slider example
Slider Example
<Matt_King> github: w3c/
MK: I have looked at it, but not commented
MK: It seems to address the issue problems
MK: My first thought is about the wording of the label, and the number of items in the scale
MK: Normally they are 10 point scales, not 11 points
MK: The scale is extremely dissatisified to extremly satisified
MK: The found the wording confusing
JG: In the previous example we just talked about stars
MK: What do people expect in a 10 point satisfaction scale
MK: Do we want words to label the numbers
JG: Let's make it simplier, use a 10 point scale
MK: We do not a 0-10 point scale in the label
CB: I think the label could be shorter
AC: Can we use 0-5 instead of 10?
MK: We radio have the radio one for the 5 point scale
MK: We wanted a longer scale to demonstrate where slider is better than radio pattern
MK: Shorten from 1-10, rather than 010
JG: The ratings will only have text labels on 1 and 10
CB: For some reason I thought value max and min are announced by JAWS
MK: We have an issue in ARIA-AT on this issue
MK: If you have aria-min and aria-max and you are using ara-valuetext
MK: aria-min and aria-max can only be numbers
JG: The range is 0-10, but the user can only select between 1-10
MK: That seems to make sense
MK: The range should be from 1 - 10, instead of 0 - 10.
JG: Our documentation says that we need a aria-valuenow between aria-valuemin and aria-valuemax
JG: Dynamically changing the range has many problems
MK: We can do what you are doing right now, since it conforms to the spec
MK: What is the screen reader going to hear if there is a minimum value
Issue 2835 - Revise landmark example pages to use site template
<Matt_King> github: w3c/
MK: Landmark example pages do not use WAI templates
MK: Problems loading the APG website
MK: We had a highlight feature on the example pages and used a range of landmarks of each page
MK: I would like to use a the APG template for the landmark page
MK: We could make an example page with all the landmark types, including FORM, SEARCH and REGION
MK: The code that is the example would be spread throughout the template
MK: Not sure how to address ther coding example
MK: The code for landmarks is simple
JG: You want to take out the coding examples, they are to simples
MK: There would be just one page in the example directory, there is not keyboard
MK: Maybe a control to highlight all or individual landmark
MK: Visually highlighting the landmarks is important
JG: I agree on the highlighting
Siri: Mostly I tell people what types of landmarks to use
MK: Do you point to the APG examples
Siri: I point them to a page using good landmarks
AC: I don't reference landmarks a ton in our work
Siri: The website is slow
JG: Landmarks are not considered a WCAG requirement and in compliance driven process there are more important
MK: The HTML defaults are both helpful and problems
JG: When people are interested landmarks what should the example tell them
MK: We ned to focus on what the landmark example page
JG: Do you want me to draft something?
MK: What is the best approach here?
MK: Some design criteria, what the biggest issue is the words on the page
<siri> https://
MK: I would like to get this done by the end of the year, what is the most important for the example page
End meeting
<Matt_King> Next meeting on Oct 17