Hey there! Brian Dys here — I’m a visual and visceral person at heart. Ever since my mom lent me her old film camera, I fell in love with photography. All of my creative musings were exemplified by my second brain, the computer. This journey is a topsy-turvy ride of creative pursuits — from electronic music to UX design.
I enjoy every dull and wild moments of it — yes, this life of mine that I share with a woman named Jaycelle and a boy named Bryce. Take a peek into my kaleidoscope!
I categorize <a> into two: Links and Actions.
Links will take you to another location, mostly for information while Actions could also do the same but with a more targeted purpose.
Links can be left alone in CSS – because they are buried in paragraphs or sitting beside other texts. Actions require styles that will enhance their usability – like padding to increase its active area (easier to click).
I’ve been reading lately about events and conferences selling “Blind Bird” tickets.
It seems like it stemmed from “Early Bird” and upon searching the term “Blind Bird Ticket” in Google, only more Blind Bird ticket sales came up. No official Wiki or definition whatsover.
Buying a Blind Bird Ticket means that you’re entitled to a hefty discount (much like an Early Bird) at an event without further details yet – such as to who will be speaking or doing the intermission numbers.
Does the HTML markup of your website has an accessibility function in the form of “Skip to Content”? If yes, then you would notice that it is located at the topmost of the markup. This is as such in order to make it the first focus when using keyboard to navigate.
Now you may ask, “Shouldn’t the document title be at the topmost of the document?”
Not when you put this accessibility function into the context of its intended use. The user, upon arriving at your website might have come from a link or have typed a URL into the web browser. That could’ve acted as the document title that ensures the user where s/he is.
The second part of this context is the user being able to go directly to the content – skipping every element that isn’t part of his or her purpose for visiting the website.
See the Pen Skip to Content by Brian Dys Sahagun (@BrianSahagun) on CodePen.
As UI designers, it’s easy to jump into sketching UIs through wire frames. Afterall, UIs are commonly visual. But taking a careful step of planning before sketching is a rewarding way of ensuring that the information embedded into the UI is well-thought of.
Awhile ago, I received a surprise in my email – that I passed the ToT post exam.
The little sacrifice of waking up early in the mornin, driving 46km to the venue, simultaneously participating in the discussion and working remotely – paid off.
I am now qualified as a lab assistant during the Web Development Training.
Branching out from HopScotch, I am reformulating mostly the front-end of the theme. Here comes Applicator – which I plan to submit to WordPress Free Themes.
The basic HTML skeleton are based on WordPress Twentyfifteen and HTML5 Boilerplate / Mobile. Basically the content of <head> are snippets from these awesome frameworks.
Currently, I am building components one by one – starting from the Masthead constructor.
If JavaScript is supported/enabled by the browser, there are two classes added in <html>:
Adds classes into <html>
