mdehoog / mdehoog/Semantic-UI-Calendar

Accessibility compliance

Open
#39 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
JavaScript
Stars
800
Forks
126
PR merge metrics
No merged PRs in 30d

Description

Hello, I use your calendar since it was a pull request on Semantic-UI repository.
I have a request for you: can you make your addon compliant with accessibility standards (WCAG 2.0)?

AChecker returns the following errors:

Check 244: Data table with both row and column headers does not use scope to identify cells.
Repair: Add scope attributes to header cells so they identify the cells that relate to the header.

Line 553, Column 237:
<table class="ui celled center aligned unstackable table seven column day"><thead><tr><th colspan="7 ...
Line 608, Column 153:
<table class="ui celled center aligned unstackable table seven column day"><thead><tr><th colspan="7 ...

Check 245: Data table with more than one row/column of headers does not use id and headers attributes to identify cells.
Repair: Add id and headers attributes to table cells so they identify the cells that relate to the headers.

Line 553, Column 237:
<table class="ui celled center aligned unstackable table seven column day"><thead><tr><th colspan="7 ...
Line 608, Column 153:
<table class="ui celled center aligned unstackable table seven column day"><thead><tr><th colspan="7 ...

Thank you.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Inspect the calendar source that generates the tables shown at lines 553 and 608, beginning with the header rows and associated cells. Verify the reported AChecker checks after adding the required table relationships; done means those two errors are resolved and the calendar remains usable with accessibility tools.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
accessibility, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.