Closed katjam closed 2 years ago
@jasminechatfield We can do the "Must do" as individual tickets but I found it useful to list them in one place.
Might be worth watching this talk ?
No that one is specifically about an elm library that bakes in accessiblity you have to use instead of the base html package.
You'd be better off watching a general accessible mark-up talk and then applying it in Elm. Want me to look for a good one for you?
I mean, having said that, if you are interested in how types might be used to enforce accessibility then yes, watch. It makes some interesting observations and was a good endeavour. I don't think the library has been widely adopted though - maybe because developers have to ultimately know how to write the accessible markup whether they use a tool to enforce it or not.
This is a pretty good overview / starting point https://developer.mozilla.org/en-US/docs/Learn/Accessibility
And if you want some videos - then these are linnked from there: https://egghead.io/courses/start-building-accessible-web-applications-today
I learned most of my fundamentals from working with Heydon in the early days of Neontribe, it was just me and him. He's pretty opinionated but has some good resources like: https://inclusivedesignprinciples.org/
I think we take this out public launch milestone. It's a huge job and we should do it with users when we have more funding.
OK. I do think it is fundamentally important though and that we ought to be doing everything with an accessible 1st attitude. It's not that big of a job if you pay attention to it as you go. We can work on this for future.
I agree, just trying to be pragmatic here. I trust you to use good accessible code as it is. I think a lot of this stuff is really nice to have but isn't going to stop anyone using the site so I see this as probably iteration 2 already.
I keep spotting accessibility issues in the code, so I've pulled this back into the public release to do a high level pass of the site. I think the action is for someone who already knows about this stuff to pull out more issues for each point (or quickly fix them).
Agree. I can take this one back and make the tickets as per the original plan. Once they are articulated we can decide on priority.
On Wed, 5 Oct 2022 at 11:16, F @.***> wrote:
I keep spotting accessibility issues in the code, so I've pulled this back into the public release to do a high level pass of the site. I think the action is for someone who already knows about this stuff to pull out more issues for each point (or quickly fix them).
— Reply to this email directly, view it on GitHub https://github.com/GenderedIntelligence/the-trans-dimension/issues/39#issuecomment-1268234902, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGSH5BOCH4NE5BGBWBGQQLWBVIQPANCNFSM5OLGPXLQ . You are receiving this because you authored the thread.Message ID: @.***>
@ivan-kocienski-gfsc can you please tick the items in must do that you completed?
Then, convert the outstanding tasks to issues - on the backlog.
After that, we can maybe close this?
Description
Run down accessibility checklist to make sure we're doing all the right things. Obviously we will be accessibility first as we build but it's worthwhile to do an audit after we have built a few pages.
Acceptance Criteria
Must do:
Should do:
Notes