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

add title and lang to increase google web accessibility score. #61

Open
gedw99 opened this issue Oct 29, 2024 · 4 comments
Open

add title and lang to increase google web accessibility score. #61

gedw99 opened this issue Oct 29, 2024 · 4 comments

Comments

@gedw99
Copy link

gedw99 commented Oct 29, 2024

<html hx-ext="path-deps, response-targets, mutation-error, htmgo, sse">

add title element

add lang param

this is common to all...

@gedw99 gedw99 changed the title add title and lang tag to increase google web speed score. add title and lang to increase google web speed score. Oct 29, 2024
@gedw99
Copy link
Author

gedw99 commented Oct 29, 2024

I can PR this . Actually could not find the code that does this in the framework . It’s a bit abstract :) if you can point me to the area it would be fab

was thinking of adding a sub command to allow use to run this on any example too .

k6 is a pretty cool system for doing web testing too.

https://github.com/grafana/k6

@gedw99 gedw99 changed the title add title and lang to increase google web speed score. add title and lang to increase google web accessibility score. Oct 29, 2024
@maddalax
Copy link
Owner

Are you referring to the meta attributes? The framework itself doesn't add it, they are defined in the starter template itself, on the RootPage

@gedw99
Copy link
Author

gedw99 commented Oct 29, 2024

Yes I am .

Ok thanks . Will have a look .

the scores for everything are 100 % btw :)

75 % for accessibility..

@gedw99
Copy link
Author

gedw99 commented Oct 29, 2024

Yep the html that needs fixing is here : https://github.com/maddalax/htmgo/blob/master/templates/starter/pages/root.go

will manually fix everything for now …

This can be manually fixed but it has 2 shortcomings:

  1. all other apps / examples miss out on the fix.
  2. We have a discussion about doing LTR / RTL already : i18n and i10 #41

I need to think about the best way for framework generated and developer generated code to alter the final html.

I suspect it starts with just adding framework level code to detect the locale etc, so that developer code can use it where needed later.

Further down the road, we will see where the framework can create the code for the developer at Run time or Generation time for these features that are common to Apps.

It’s important that certain things are opt in. Maybe all things ..

If anyone has thoughts on this would love to hear it .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants