Ghost is gone, but any of these seem like good ideas. I do wonder about keyboard navigation; what if we used vim-style j/k to move up and down through the list?

I would be interested in pursuing this a11y update.

I opened pull request #994 that hopefully ticks two of the above boxes.

• Include labels for inputs (helps with screen reader accessibility even if visibly hidden)

• Add ARIA attributes such as "roles" and "describedby"

• Improve keyboard navigation (I suggest that tabbing moves between project titles and skips project tags & "up-for-grabs" label)

• Improve semantic HTML use by, for example, fixing nonconsecutive heading level use (many h1 tags) without altering visual presentation of course

• Improve overall screen reader experience (humanise descriptions to avoid, for example, “Select a tag ellipsis edit text”)

I'm still very new to github issues, so if @alexandraholcombe or @dahlbyk have advice for these and other improvements, I'd be very open to them! : )

Update: I've been working on the semantic HTML use, ended up consulting some a11y experts at my company in regards to some options. PR is forthcoming, probably next day or two.

I can add ARIA attributes

@catherineluse Please go with it. Thanks for taking interest :)

Good day, May I know the update on this issue

I should unassign myself

@bellomuboye you can take it up

I could probably help with this if we still want to work on it?

@ConnorAhern Yep, feel free to.

Hey, can I work on this? If yes, then do I need to work on all the issues mentioned here or can I pick and choose?

Hi, I'm a new dev + new to open source, and . But I am a former special ed teacher/assistive tech specialist. I'd love to contribute to this issue.