Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Encoding Errors on the archive-page.html #286

Open
1 task done
OmarAmeen01 opened this issue Oct 23, 2024 · 1 comment
Open
1 task done

[Bug] Encoding Errors on the archive-page.html #286

OmarAmeen01 opened this issue Oct 23, 2024 · 1 comment
Labels
💻 aspect: code Concerns the software code in the repository 🛠 goal: fix Bug fix 🟩 priority: low Low priority and doesn't need to be rushed 🧹 status: ticket work required Needs more details before it can be worked on

Comments

@OmarAmeen01
Copy link
Contributor

Description

There are lot of encoding error on the archive-page.html eg

  1. Expected omitted end tag<link> instead of self-closing element<link/>
  2. Landmarks must have a non-empty and unique accessible name (aria-label or aria-labelledby)
  3. <button> is missing recommended "type" attribute-o-implicit-button-type
  4. <img> is missing required "alt" attribute
  5. Raw ">" must be encoded as"&gt;"
  6. Expected omitted end tag <br> instead of self-closing element <br/>

Reproduction

  1. install html-validate as global dependency
  2. runhtml-validate specimen/contexts/archive-page.html
  3. see the errors

Expectation

these characters should replaced with the appropriate html entity and adding missing parts to the suggested elements

Environment

  • Device: (_iPhone Xs; laptop)
  • OS: (iOS 13.5; Fedora 32)
  • Browser: ( Safari; Firefox)
  • Version: (13; 73)
  • Other info: (display resolution, ease-of-access settings)

Additional context

Resolution

  • I would be interested in resolving this bug.
@OmarAmeen01 OmarAmeen01 added 💻 aspect: code Concerns the software code in the repository 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🛠 goal: fix Bug fix 🟧 priority: high Stalls work on the project or its dependents labels Oct 23, 2024
@possumbilities
Copy link
Contributor

Hi @OmarAmeen01 I would urge you to look at #283 and as you split up items, try to combine them if they are repeating across contexts.

This Issue is also a combination of a number of items that should largely be split up into several individual Issues.

@possumbilities possumbilities added 🧹 status: ticket work required Needs more details before it can be worked on 🟩 priority: low Low priority and doesn't need to be rushed and removed 🟧 priority: high Stalls work on the project or its dependents 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Oct 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository 🛠 goal: fix Bug fix 🟩 priority: low Low priority and doesn't need to be rushed 🧹 status: ticket work required Needs more details before it can be worked on
Projects
Status: Backlog
Development

No branches or pull requests

2 participants