nextcloud / nextcloud/polls

[A11Y] Contrast Issues

Open
#4,784 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

UX
Dominant language
JavaScript
Stars
284
Forks
91
Avg merge
4d 3h
Merged PRs (30d)
50

Description

Elements found:

The subtitle of the private poll is not accessible
Image

The yellow 0 is not accessible
Image

⚠️ This issue respects the following points: ⚠️
  • This is a bug, not a question or a configuration/webserver/proxy issue.
  • This issue is not already reported on Github (I've searched it).
  • I agree to follow Nextcloud's Code of Conduct.
What went wrong, what did you observe?

Certain text in this app doesn't pass the WCAG AA standard

What did you expect, how polls should behave instead?

All the text in the app should pass WCAG AA standard

What steps does it need to replay this bug?
  1. Open mentioned parts of app, use extension like WCAG Color contrast checker
Affected polls version

main

Installation method

Installed/updated from the appstore (Apps section of your site)

Installation type

First time installation

Can you rule out that any extension you use is involved in the issue?
  • I have checked all browser extension
Which browser did you use, when experiencing the bug?
  • Firefox
  • Chrome
  • Chromium/Chromium based (i.e. Edge)
  • Safari
  • Other/Don't know
Other browser

No response

Add your browser log here

Additional client environment information

No response

NC version

Nextcloud 33 (Hub 26 Winter)

Other Nextcloud version

No response

PHP engine version

PHP 8.1

Other PHP version

No response

Database engine

MySQL

Database Engine version or other Database

No response

Which user-backends are you using?
  • Default user-backend (database)
  • LDAP/ Active Directory
  • SSO - SAML
  • Other/Don't know
Add your nextcloud server log here

Additional environment informations

No response

Configuration report

List of activated Apps

Nextcloud Signing status

Additional Information

No response

Contributor guide

Open the contributing guide

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

Open the private poll and inspect the subtitle and yellow “0” shown in the issue screenshots with a WCAG color-contrast checker. Trace those elements to their frontend implementation, then verify that both meet the WCAG AA contrast standard in the relevant poll views.

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
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.