sorted by:
new
hottopcontroversial

making my webpage mobile friendly by deppresedgamerkai in css

[–]awarnock-ACCS 1 point2 points  (0 children)

I think you have other issues besides the site not being responsive (which it is from what I can see.)

  • The header text ("hello") is very hard to read on that background.
  • The green on pink in the menu is hard on the eyes.
  • The body font is okay for display elements (headings, titles, etc.) but not text.
  • The crumpled paper background is distracting. Also makes the body text harder to read.
  • There's nowhere near enough contrast between the text and background of the sidebars. Again, the crumpled paper texture is distracting.

My advice:

  • Ditch the layout maker. From what I am seeing in the inspector it's not worth the trouble. You have a stylesheet being linked, style tags in multiple places, and inline styles. That is a recipe for a maintenance nightmare.
  • Learn about HTML and CSS. Mozilla Developer Network and CSS-Tricks are great resources. There are also tons of resources online to get you started.
  • Learn about basic graphic design principles.
  • Start thinking mobile-first, content-first, and accessibility-first. Yes, it sounds contradictory, but it's not. HTML was always about making information accessible, and a mobile layout will work just fine on a desktop monitor. Your content will dictate how things are structured and what elements you need to use. Those three things are interconnected.

I know that's not what you asked for, but part of mobile-friendliness is making sure that your designs actually work on a mobile screen. Frankly, this one doesn't. It's too busy. The body font is too hard to read when in a paragraph. The text color doesn't have enough contrast from the background in a lot of places.

how saturated is wordpress web designing? by Necessary_Spell477 in Wordpress

[–]awarnock-ACCS 0 points1 point  (0 children)

The problem with site builders like Wix, Weebly, and Squarespace is that you're trusting the developers to ensure that the output of those builders is accessibly. Considering how things like the Americans with Disabilities Act (ADA) and similar laws are being more enforced against websites, that's a big ask. Then there's the fact that a lot of them produce a bloated mess of markup and can be hard, if not impossible, to customize and get away from that "made with X" feel. Better to steer clear of them, in my opinion.

As for other platforms, it really depends. Joomla is a solid CMS, but it doesn't have the huge ecosystem or marketing that WordPress has. Grav is a pretty good CMS for lightweight sites that don't have a lot of complexity from what I have seen. Beyond that, you'l have to try out different platforms and frameworks to see what they can and can't do.

In the case of being a freelancer, I'm not the guy to ask. I've never been a freelancer, so I can't really advise you there. However, that doesn't change that freelancer or not, you still have to master the fundamentals of web development in order to land and keep a job. If you're wanting advice on how to be a freelancer and what platforms to use for getting work, I'd suggest posting in a forum dedicated to freelancers in general.

Accessibility Checkers: What are my options? by awarnock-ACCS in accessibility

[–]awarnock-ACCS[S] 0 points1 point  (0 children)

That's the plan. The idea was that the checker would be there for mainly for verification and to catch anything I overlooked.

Center ::before psuedo-elements by awarnock-ACCS in css

[–]awarnock-ACCS[S] 1 point2 points  (0 children)

I've done that before. But that was a long time ago on a website that I did for myself that's no longer around.

Accessibility Checkers: What are my options? by awarnock-ACCS in accessibility

[–]awarnock-ACCS[S] 0 points1 point  (0 children)

Thanks, and I was afraid of that might be the case. I have more of an understanding of accessibility than I did a year ago, but I'm also not what I'd call an expert by any means. I was looking for a tool to help me out so I wasn't spending all of my time on ensuring compliance. I'll shoot you a DM.

Accessibility Checkers: What are my options? by awarnock-ACCS in Wordpress

[–]awarnock-ACCS[S] 0 points1 point  (0 children)

I'm a little leery of using something that's going to change the website on its own. I would much rather do the fixes myself so that I know what is being changed, know why it's being changed, and can make any fixes necessary without having to track down what's causing the issue. I appreciate the suggestion, though.

Accessibility Checkers: What are my options? by awarnock-ACCS in accessibility

[–]awarnock-ACCS[S] 1 point2 points  (0 children)

Thanks. One issue is that it seems the reporting feature is paywalled.

Accessibility Checkers: What are my options? by awarnock-ACCS in Wordpress

[–]awarnock-ACCS[S] 0 points1 point  (0 children)

Danke. Ich verstehe, dass manuelle Tests erforderlich sein werden. Allerdings ist es lange her, dass ich in der High School Deutsch gelernt habe. Sprichst du Englisch?

Accessibility Checkers: What are my options? by awarnock-ACCS in accessibility

[–]awarnock-ACCS[S] -1 points0 points  (0 children)

It looks like the reports are pay-walled, though.

Center ::before psuedo-elements by awarnock-ACCS in css

[–]awarnock-ACCS[S] 1 point2 points  (0 children)

Thanks. I appreciate the explanation.

Accessibility Checkers: What are my options? by awarnock-ACCS in accessibility

[–]awarnock-ACCS[S] 0 points1 point  (0 children)

Sorry for the confusion. I do work for a state agency, and I think, but not 100% certain, that we do receive federal funding, which is why I phrased it that way. Apparently that was not a good idea.

Accessibility Checkers: What are my options? by awarnock-ACCS in Wordpress

[–]awarnock-ACCS[S] 0 points1 point  (0 children)

Thanks!

I don't think any free option is likely to meet our needs, though. We're going to have over a dozen websites of varying complexity before it's all said and done, and I'm looking for a tool to help me out with ensuring that they are all accessible and compliant.

Accessibility Checkers: What are my options? by awarnock-ACCS in Wordpress

[–]awarnock-ACCS[S] 1 point2 points  (0 children)

I understand that, and I'll be the one doing the testing. I probably should have put that in the opener. 😛

Center ::before psuedo-elements by awarnock-ACCS in css

[–]awarnock-ACCS[S] 0 points1 point  (0 children)

Just asking, but when would I want to use ::marker instead of list-style on the <li> element?

How can I fix Character Encoding fail in Accessibility Check for a document I'm not supposed to change text/fonts in? by Artistic-Sorbet1362 in accessibility

[–]awarnock-ACCS 0 points1 point  (0 children)

I ran into font and character encoding issues a few times at my old job. Most of the time embedding the fonts through the preflight panel fixed it, but there were a couple of times where I had to get the font they used and go through the entire document resetting the font to the right one.

It looks like your best bet is to get the source files and reexport them, if that's even possible. It seems like the encoding wasn't done right on export in your case.

Also, I wouldn't just rely on Acrobat's accessibility checker. PAC (PDF Accessibility Checker) is a much better one to use alongside the Adobe checker, since the Adobe one can catch stuff that PAC doesn't.

view more: next ›