Accessibility Specialist. I focus on ensuring content created, events held and company assets are as accessible as possible, for as many people as possible.
Don't use tables for layout (your profile picture bit and your skills bit). This is really important for people who use a screen reader (a piece of software that reads the page aloud, normally used by people with a vision impairment).
Instead of tables look into using semantic HTML with CSS.
Learn how to use the correct elements depending on content and you will already be better than 90% of developers and massively increase your job prospects when the time comes!
So swap the table at the top for some <div>s and perhaps wrap them in a <section> element.
I will leave you to research those but if you need any help understanding any of them just let me know.
Forms
Along the same lines you contact form is not accessible either.
In the following example I have corrected a few things:-
I added for="IDofElement" to your labels and a corresponding ID to the input. This links them together which means people who use a screen reader here what the input is called (otherwise it will just read "input" which is not very useful!) and has the added bonus of making it so you can click the label to focus the corresponding input.
I changed your <input type="submit"> to a <button>. That is the correct way to do it in modern HTML.
I added type="email" to the email field as this offers some basic validation (to check someone entered an email in the correct format).
<formclass=""action="mailto:xxxxDONT INCLUDE YOUR EMAIL IN EXAMPLES TO AVOID SPAMMERSxxx"method="post"enctype="text/plain"><labelfor="your-name">Your Name</label><inputtype="text"name="Your Name"value=""id="your-name"><br/><labelfor="your-email">Your email</label><inputtype="email"name="Your Email"value=""type="email"id="your-email"><br/><labelfor="your-message">Your Message</label><br/><textareaname="Your Message"rows="10"columns="30"id="your-message"></textarea><br/><buttontype="submit">Submit</button></form>
Navigation
Navigation is really important on a site, every page should ideally have your main menu at the top.
So we use a <header> element to represent introductory content.
We then put a <nav> element within the <header> as that signifies navigation. This helps people who use a screen reader know that they have reached the site navigation.
We then use an <ul> and <li> to add each of the hyperlinks. Yet again this is really useful for people who use a screen reader as they will be told "item 1 of 3" when they enter the navigation so they know how many menu items there are.
One thing I didn't include was handling "current page" - there are numerous ways to do that but I didn't want to completely over load you!
Add navigation to each of the pages so that when someone visits your "hobbies" page they can still get to the contact page and the home page easily.
I hope I didn't overload you!
That is probably a couple of weeks worth of things to learn in one comment so don't be overwhelmed.
Just tackle them one at a time and as I said, if you need help, just shout!
A few things to be aware of:
Tables
Don't use tables for layout (your profile picture bit and your skills bit). This is really important for people who use a screen reader (a piece of software that reads the page aloud, normally used by people with a vision impairment).
Instead of tables look into using semantic HTML with CSS.
Learn how to use the correct elements depending on content and you will already be better than 90% of developers and massively increase your job prospects when the time comes!
So swap the table at the top for some
<div>s and perhaps wrap them in a<section>element.Swap the table at the bottom for a
dlor similar.I will leave you to research those but if you need any help understanding any of them just let me know.
Forms
Along the same lines you contact form is not accessible either.
In the following example I have corrected a few things:-
for="IDofElement"to your labels and a corresponding ID to the input. This links them together which means people who use a screen reader here what the input is called (otherwise it will just read "input" which is not very useful!) and has the added bonus of making it so you can click the label to focus the corresponding input.<input type="submit">to a<button>. That is the correct way to do it in modern HTML.type="email"to the email field as this offers some basic validation (to check someone entered an email in the correct format).Navigation
Navigation is really important on a site, every page should ideally have your main menu at the top.
Navigation should be something like:-
So we use a
<header>element to represent introductory content.We then put a
<nav>element within the<header>as that signifies navigation. This helps people who use a screen reader know that they have reached the site navigation.We then use an
<ul>and<li>to add each of the hyperlinks. Yet again this is really useful for people who use a screen reader as they will be told "item 1 of 3" when they enter the navigation so they know how many menu items there are.One thing I didn't include was handling "current page" - there are numerous ways to do that but I didn't want to completely over load you!
Add navigation to each of the pages so that when someone visits your "hobbies" page they can still get to the contact page and the home page easily.
I hope I didn't overload you!
That is probably a couple of weeks worth of things to learn in one comment so don't be overwhelmed.
Just tackle them one at a time and as I said, if you need help, just shout!
Thank you for pointing it out I will surely work on these